Method, apparatus and system for processing an access request in a content delivery system

ABSTRACT

An access request processing method for a content delivery system includes obtaining a file access request; judging, according to a preset unpopular file judgment policy, whether a file corresponding to the file access request is an unpopular file; in response to determining that the file is an unpopular file, judging whether bandwidth usage state information obtained in advance conforms to a preset judgment policy for full use of bandwidth; and triggering, in response to determining that the bandwidth usage state information conforms to the judgment policy, an unpopular file management node to respond to the file access request. The unpopular file management node stores the file corresponding to the file access request.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a national stage entry under 35 U.S.C. § 371of International Application No. PCT/CN2020/103439, filed on Jul. 22,2020, which claims priority to Chinese Patent Application No.201910694947.X, titled “METHOD, APPARATUS AND SYSTEM FOR PROCESSING ANACCESS REQUEST IN A CONTENT DELIVERY SYSTEM,” filed to the StateIntellectual Property Office of People's Republic of China on Jul. 30,2019, which are incorporated herein by reference in their entirety.

TECHNICAL FIELD

The present application relates to, but is not limited to, the field ofcommunications, and in particular to a method, apparatus and system forprocessing an access request in a content delivery system.

BACKGROUND

The Content Delivery Network (CDN), the purpose of this network is toavoid bottlenecks and links on the Internet that may affect the speedand stability of data transmission, so that content transmission isfaster and more stable. As an intelligent virtual network based on theexisting Internet and including node severs placed at various places inthe network, the CDN system can redirect in real time a request from auser to a service node closest to the user according to the networktraffic, the connectivity and loads of nodes, the distances to the user,the response times, etc., so that the user can obtain the desiredcontent nearby. The network congestion of the Internet is solved, andthe response speed for the user to access the website is improved.

In a content delivery network, in order to ensure resource redundancyand fault backup, it is common to use dozens or hundreds of clouddelivery edge nodes to provide file caching services for a same customerand a same business; moreover, for resource files for one business,there is always a situation where unpopular resource files and hotresource files are mixed and difficult to be distinguished. Therefore,in an actual production environment, multiple end customers may randomlyrequest a same unpopular file from multiple edge nodes. As a result, allthe multiple edge nodes need to request a same unpopular file from theirupstream nodes. In addition, the unpopular resource files are almostnever accessed again after being cached.

These two scenarios will lead to a lot of bandwidth cost consumption andstorage resource consumption in a cloud content delivery network,resulting in the waste of network resources.

SUMMARY

In order to overcome the problems in related technologies, the presentapplication provides a method, apparatus and system for processing anaccess request in a content delivery system.

According to a first aspect of the present application, a method forprocessing an access request in a content delivery system is provided,comprising:

obtaining a file access request;

judging, according to a preset unpopular file judgment policy, whether afile corresponding to the file access request is an unpopular file, toobtain a judgment result;

judging, if the judgment result shows that the file is an unpopularfile, and according to bandwidth usage state information obtained inadvance, whether the bandwidth usage state information conforms to apreset judgment policy for a full use of a bandwidth, to obtain ajudgment result; and

triggering, when the judgment result shows that the bandwidth usagestate information conforms to the judgment policy, an unpopular filemanagement node to respond to the file access request, wherein theunpopular file management node stores the file corresponding to the fileaccess request.

Wherein, the judging, according to a preset unpopular file judgmentpolicy, whether a file corresponding to the file access request is anunpopular file, to obtain a judgment result comprises:

searching, among locally stored files, a file corresponding to fileidentification information; and

determining, if the file is not found among the locally stored files, astate of the file according to a judgment policy for a popularity of afile obtained in advance.

Wherein, the judging, according to bandwidth usage state informationobtained in advance, whether the bandwidth usage state informationconforms to a preset judgment policy for a full use of a bandwidth, toobtain a judgment result comprises:

obtaining a first number of file access requests to which the unpopularfile management node has been triggered to respond and a total number offile access requests obtained;

judging, according to the first number and the total number, whetherproportion information of the first number in the total number conformsto a preset judgment policy for an excessive proportion; and

determining, if the proportion information does not conform to thejudgment policy for an excessive proportion, that the bandwidth usagestate information conforms to the judgment policy for a full use of abandwidth.

Wherein, the triggering an unpopular file management node to respond tothe file access request comprises:

obtaining, when there are at least two unpopular file management nodes,region information and/or operator network information used to transmitinformation for each unpopular file management node;

selecting, according to the region information and/or operator networkinformation for each unpopular file management node, a target unpopularfile management node, the target unpopular file management nodeconforming to local region information and/or operator networkinformation; and

controlling the target unpopular file management node to respond to thefile access request.

Wherein, the selecting, according to the region information and/oroperator network information for each unpopular file management node, atarget unpopular file management node, the target unpopular filemanagement node conforming to local region information and/or operatornetwork information comprises:

obtaining domain name resolution information corresponding to the fileaccess request; and

determining, according to the domain name resolution information and theregion information and/or operator network information for eachunpopular file management node, an unpopular file management nodematching the domain name resolution information among the unpopular filemanagement nodes as the target unpopular file management node.

According to a second aspect of the present application, an apparatusfor processing an access request in a content delivery system isprovided, comprising:

an obtaining module configured to obtain a file access request;

a first judgment module configured to judge, according to a presetunpopular file judgment policy, whether a file corresponding to the fileaccess request is an unpopular file, to obtain a judgment result;

a second judgment module configured to judge, if the judgment resultshows that the file is an unpopular file, and according to bandwidthusage state information obtained in advance, whether the bandwidth usagestate information conforms to a preset judgment policy for a full use ofa bandwidth, to obtain a judgment result; and

a processing module configured to trigger, when the judgment resultshows that the bandwidth usage state information conforms to thejudgment policy, an unpopular file management node to respond to thefile access request, wherein the unpopular file management node storesthe file corresponding to the file access request.

Wherein, the first judgment module comprises:

a searching unit configured to search, among locally stored files, afile corresponding to file identification information; and

a first obtaining unit configured to determine, if the file is not foundamong the locally stored files, a state of the file according to ajudgment policy for a popularity of a file obtained in advance.

Wherein, the second judgment module comprises:

a second obtaining unit configured to obtain a first number of fileaccess requests to which the unpopular file management node has beentriggered to respond and a total number of file access requestsobtained;

a judgment unit configured to judge, according to the first number andthe total number, whether proportion information of the first number inthe total number conforms to a preset judgment policy for an excessiveproportion; and

a determination unit configured to determine, if the proportioninformation does not conform to the judgment policy for an excessiveproportion, that the bandwidth usage state information conforms to thejudgment policy for a full use of a bandwidth.

Wherein, the processing module comprises:

a third obtaining unit configured to obtain, when there are at least twounpopular file management nodes, region information and/or operatornetwork information used to transmit information for each unpopular filemanagement node;

a selection unit configured to select, according to the regioninformation and/or operator network information for each unpopular filemanagement node, a target unpopular file management node, the targetunpopular file management node conforming to local region informationand/or operator network information; and

a control unit configured to control the target unpopular filemanagement node to respond to the file access request.

Wherein, the selection unit comprises:

an obtaining sub-module configured to obtain domain name resolutioninformation corresponding to the file access request; and

a determination sub-module configured to determine, according to thedomain name resolution information and the region information and/oroperator network information for each unpopular file management node, anunpopular file management node matching the domain name resolutioninformation among the unpopular file management nodes as the targetunpopular file management node.

According to another aspect of the present application, a contentdelivery system is provided, comprising:

an edge node, comprising the apparatus described above; and

an unpopular file management node configured to respond to a file accessrequest.

Wherein, the system further comprises:

a decision-making center configured to obtain file access information ina file access request that occurs within a preset period of time and/ornetwork bandwidth usage information corresponding to the file accessrequest, and according to the file access information and/or networkbandwidth usage information, determine a judgment policy for apopularity of a file, and then send the judgment policy for a popularityof a file to the edge node.

The unpopular file management node is configured to respond a fileaccess request with a corresponding file in a local storage space if thefile corresponding to the file access request is found locally, andrequest the file corresponding to the file access request from anupstream node if the file corresponding to the file access request isnot found locally;

Wherein, the system further comprises:

an upstream node configured to obtain a corresponding file from a localstorage space upon receiving a request for a file from an unpopular filemanagement node, and send the corresponding file to the unpopular filemanagement node.

Wherein, the unpopular file management node is configured to obtainproportion information of file access requests to which the unpopularfile management node is triggered to respond by the edge node and allfile access requests obtained, and determine a capacity of a storagepool of the unpopular file management node according to the proportioninformation and a capacity of a storage pool of the edge node.

According to another aspect of the present application, there isprovided a computer-readable storage medium having a computer programstored thereon, and the computer program, when executed by a processor,implements the method described above.

According to another aspect of the present application, a computerdevice is provided, comprising a processor, a memory, and a computerprogram stored on the memory, and the computer program, when executed bythe processor, implements the method described above.

In the present application, a file access request is obtained; it isjudged, according to a preset unpopular file judgment policy, whether afile corresponding to the file access request is an unpopular file, toobtain a judgment result; it is judged, if the judgment result showsthat the file is an unpopular file, and according to bandwidth usagestate information obtained in advance, whether the bandwidth usage stateinformation conforms to a preset judgment policy for the full use of thebandwidth, to obtain a judgment result; and when the judgment resultshows that the bandwidth usage state information conforms to thejudgment policy, an unpopular file management node is triggered torespond to the file access request. By judging whether an unpopular filemanagement node is triggered to respond to a file access request for anunpopular file, the forwarding of local file access requests to othernodes is effectively controlled, thereby controlling the number offorwarded requests. The file processing efficiency is improved whileensuring the full utilization of the local resources.

It should be understood that, the aforementioned general description anddetailed description hereinafter are merely exemplary and explanatory,and the present application is not limited thereto.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings illustrated herein, which constitute part ofthe present application, are used to provide further understanding ofthe present application, and exemplary embodiments of the presentapplication and the description thereof are used to explain the presentapplication and not intended to inappropriately limit the presentapplication. In the drawings:

FIG. 1 is a flowchart of a method for processing an access request in acontent delivery system according to an exemplary embodiment;

FIG. 2 is a schematic view of a method for processing an access requestaccording to an exemplary embodiment;

FIG. 3 is a schematic comparison view of a method for processing anaccess request according to an exemplary embodiment;

FIG. 4 is a schematic view of an apparatus for processing an accessrequest in a content delivery system according to an exemplaryembodiment; and

FIG. 5 is a block diagram of a computer device according to an exemplaryembodiment.

DETAILED DESCRIPTION

The technical solutions in the embodiments of the present applicationwill be described clearly and completely with reference to theaccompanying drawings in the embodiments of the present application.Apparently, the embodiments to be described are some embodiments of thepresent application, rather than all embodiments of the presentapplication. Based on the embodiments of the present application, allother embodiments obtained by a person of ordinary skill in the artwithout paying any creative effort are included in the protection scopeof the present application. It is to be noted that the embodiments ofthe present application and features in the embodiments may be combinedif not conflict.

In view of the above situation, it was found that the reason for thewaste of resources in the related technologies is the planning ofresource usage in the cloud delivery network in the relatedtechnologies. Generally, first, the required resource pool is plannedaccording to the customers' business volume, and the planned resourcepool is provided to end customers for their accessing. No attention ispaid to the popularity of files in the customers' businesses.

Since no attention is paid to the popularity of files, followingresource wastes will be caused in the content delivery network,including:

when multiple end customers access an unpopular resource file onmultiple edge nodes, the edge nodes each need to request a resource filefrom their upstream nodes, resulting in great bandwidth resourceconsumption; and

when multiple end customers access an unpopular resource file onmultiple edge nodes, the edge nodes each need to cache a resource filelocally, resulting in great storage resource consumption.

Based on the technical analysis provided by the inventor, the presentapplication provides the following solutions, including:

An exemplary embodiment of the present application provides a contentdelivery system, comprising:

an edge node, comprising an apparatus for processing an access requestin a content delivery system, wherein the apparatus is configured toobtain a file access request; judge, according to a preset unpopularfile judgment policy, whether a file corresponding to the file accessrequest is an unpopular file, to obtain a judgment result; judge, if thejudgment result shows that the file is an unpopular file, and accordingto bandwidth usage state information obtained in advance, whether thebandwidth usage state information conforms to a preset judgment policyfor the full use of the bandwidth, to obtain a judgment result; andtrigger, when the judgment result shows that the bandwidth usage stateinformation conforms to the judgment policy, an unpopular filemanagement node to respond to the file access request; and

an unpopular file management node, configured to respond to the fileaccess request, wherein the unpopular file management node stores thefile corresponding to the file access request.

In an exemplary embodiment, the edge node is a node in the clouddelivery network, which is configured to cache the content from thecustomer's origin server, and a node that can quickly respond torequests from users in different regions. In the content deliverysystem, each edge node may be configured with the apparatus, or, some ofedge nodes may be configured with the apparatus.

In an exemplary embodiment, the system may further comprise an upstreamnode, connected to the edge node, and configured to provide dataservices for the edge node. The upstream node may be the origin serverof the customer; or, it may be a cloud delivery intermediate node(intermediate source), which is specifically used to serve the edge nodein the cloud delivery process and configured to reduce part of theprocessing pressure of the edge node, thus to reduce the processingpressure of the origin server.

In an exemplary embodiment, the unpopular file management node isconfigured to store unpopular files in the content delivery system. Theunpopular file management node may be an edge node which is an edge nodefor receiving unpopular resource file requests, receiving all requestsjudged as unpopular resources, and redirecting all requests judged asunpopular resources to the corresponding resource pool through the 302technology. Similar to the maintenance method of edge nodes in therelated technologies, the difference is that the stored data is allunpopular files in the content delivery system. When deploying anunpopular file management node, because the unpopular file managementnode can serve all edge nodes collectively, during the actual deploymentof the unpopular file management node, preferably, one node is deployedto respond to all the edge nodes' requests for unpopular files. Thissaves the hardware cost. To select a node as an unpopular filemanagement node, an edge node may be used as an unpopular filemanagement node. In this way, the special management of unpopular filesis realized while retaining the original system architecture, theversatility of the solution is improved, and the maintenance cost isreduced.

In an exemplary embodiment, the unpopular file management node isconfigured to obtain proportion information of file access requests towhich an unpopular file management node is triggered to respond by theedge node and all file access requests obtained, and determine thecapacity of a storage pool of the unpopular file management nodeaccording to the proportion information and the capacity of a storagepool of the edge node.

The resource pool of the unpopular file management node is configured tostore files judged as unpopular resources. Since the bandwidth used byunpopular resource file requests to the total bandwidth is usuallybetween 5% and 10%, the size of the resource pool is much smaller thanthe size of the resource pool of the edge node in the relatedtechnologies.

The result of judging whether a file is unpopular may be changed. Whenthe business volume accessing unpopular files increases, the originalunpopular resource files may become popular resource files; and when thebusiness volume decreases, the original popular resource files maybecome unpopular resource files. For the files stored in the resourcepool of the unpopular file management node, since the popularity of thefiles may be changed, the unpopular file management node stores filesthat conform to the current unpopular file judgment policy. For storedfiles that do not conform to the unpopular file judgment policy, theyare deleted from the resource pool; and for non-stored files thatconform to the unpopular file judgment policy, they are added to theresource pool of the unpopular file management node.

In an exemplary embodiment, the unpopular file management node isconfigured to respond the file access request with a corresponding filein a local storage space if the file corresponding to the file accessrequest is found locally, and request the file corresponding to the fileaccess request from an upstream node if the file corresponding to thefile access request is not found locally;

Wherein, the system further comprises:

an upstream node configured to obtain a corresponding file from thelocal storage space after receiving a request for the file from anunpopular file management node, and send the corresponding file to theunpopular file management node.

The upstream node corresponding to the unpopular file management nodemay store unpopular files. When the unpopular file is not stored in theresource pool of the unpopular file management node, the response to thefile access request is completed by obtaining the file from the upstreamnode. By deploying the upstream node, the storage pressure of theunpopular file management node may be reduced.

The present application proposes an unpopular file judgment policy tojudge unpopular files, which is used to ensure that the files maintainedby the unpopular file management node conform to the unpopular filedetermination policy and ensure that the unpopular file management nodecan accurately maintain unpopular files.

Wherein, the unpopular file judgment policy may be determined by anewly-added decision-making center in the system, or may be determinedby the edge node itself according to the access situation.

In an exemplary embodiment, the system further comprises:

a decision-making center configured to obtain file access information ina file access request that occurs within a preset period of time and/ornetwork bandwidth usage information corresponding to the file accessrequest, and according to the file access information and/or networkbandwidth usage information, determine a judgment policy for thepopularity of a file, and then send the judgment policy for thepopularity of the file to an edge node.

Based on the description of the decision-making center, it may bedetermined that the decision-making center has the following functions:

(1) Collection of customers' access data;

In an exemplary embodiment, the accessed file information, access timeinformation, etc. are recorded.

(2) Collect the current operation situation of the separation schedulingfor the popularity of files;

In an exemplary embodiment, the access data of the end customer ismainly analyzed by analyzing the end customers' access times todifferent resources, the generated access bandwidth, and the generatededge-to-upstream bandwidth. The proportion of requests for unpopularfiles (bandwidth) in the total requests (bandwidth) under differentpopularity judgment conditions, the reduced bandwidth used for returningto the upstream, and the reduced storage consumption for the edge nodeare predicted.

When there are n edge nodes in the entire network, if there are N_(ij)files already accessed for j times on the i_(th) edge node and theaverage file size is S, then, according to the above data, the followingprediction data may be obtained when files with the number of accessesless than k are considered as unpopular files:

Proportion of the bandwidth for requests for unpopular files to thetotal bandwidth=bandwidth for unpopular files/totalbandwidth=Σ_(i=1→n)(Σ_(j=1→k)(N_(ij)*j))/Σ_(i=1→n)(Σ_(j=1→+∞)(N_(ij)*j)).

Reduced proportion of bandwidth used for returning to theupstream=reduced bandwidth used for returning to the upstream/originalbandwidth used for returning to theupstream=Σ_(i=1→n)(Σ_(j=1→k)(N_(ij)))/Σ_(i=1→n)(Σ_(j=1→+∞)(N_(ij))).

In this case, the reduced storage consumption of the edge node is:Σ_(i=1→n)(Σ_(j=1→k)(N_(ij)*S)).

(3) Providing a judgment policy for the popularity of a file based onthe access data and operating conditions;

In an exemplary embodiment, a judgment policy for popularity conditionis provided based on the access data and operating conditions. Thejudgment policy may be that a file with a total number of accesses lessthan a certain value within a preset period of time is an unpopularfile.

(4) Synchronization of the judgment policy for the popularity of a fileto the edge nodes;

The judgment policy may be sent to all edge nodes together, or sent toall edge nodes in batches.

When the decision-making center is not used to determine the judgmentpolicy for the popularity of a file, the judgment policy for thepopularity of a file may be directly made by the edge node according tothe end customers' access to the node and the node's unpopularity fileseparation condition, independent of the decision-making data of thedecision-making center.

In the present application, the judgment policy for the popularity of afile may be determined by the edge or the decision-making center. Thetwo methods are technically analyzed, specifically:

Generation of a judgment policy by the decision-making center: the fileaccess situation in the entire network is collected and analyzed, thenumber of accesses to each file is counted, and a list of unpopularfiles or a list of popular files is generated and synchronized to theedge. Wherein, the content selected for synchronization is determinedaccording to the number of lists. The smaller the data size, the lowerthe synchronization cost. After receiving the list of unpopular files(list of popular files), the edge node loads it into the serviceapplication. For each request from the end customer, a query isperformed to determine whether the request is in the list of unpopularfiles (list of popular files). If the request is in the list ofunpopular files (list of popular files), it is a request for unpopularfiles (request for popular files).

The advantage of this method is that, after the business changes, thedecision-making center can perceive this change and adjust the policy.The judgment policy for the popularity of a file made by thedecision-making center is more consistent with the data popularity ofthe entire business of the customer. Correspondingly, this method hasdisadvantages that the decision-making center needs to collect andanalyze the access situation, which proposes high requirements for thedecision-making center; and both the edge and the center need tomaintain a large list of unpopular files (list of popular files).Because the judgment policy for the popularity of a file must have hightimeliness and a guarantee mechanism needs to be provided, themaintenance cost is high. The central policy may not conform to allnodes even conforming to the entire access situation.

Generation of a judgment policy by making the decision by the edge:before the business goes online, the access situation in the entirenetwork is collected for statistical analysis, and a judgment policy forthe popularity of the file is made according to the popularity of thebusiness and issued to the edge (for example, if 65% files in the entirenetwork are accessed less than five times and the access bandwidth isabout 10%, and if 25% files in the entire network are accessed more thantwenty times and the access bandwidth is about 60%, then the judgmentpolicy for the popularity of the file is that files accessed less thanfive times are unpopular files).

Making the decision by the edge: when the edge node accepts the requestand fails to find the file in the local storage application, it checksthe number of times the file has been accessed and the judgment policyfor the popularity of the file (taking, as an example, files accessedless than five times being unpopular files). If the file is accessedless than five times, the request will be considered as a request forunpopular files and then redirected, and the number of accesses is addedby 1. If the file is accessed more than five times, the request will beconsidered as a request for popular files. The advantage of this methodis that the popularity of the file is updated in real time, and there isno need for central decision-making, which is easier for implementationand maintenance. There is no need to maintain and synchronize the listof unpopular files/list of popular files, and there may be fewer lists.The edge judges the popularity of the file according to the accesssituation, which better conforms to the serving condition of the nodeitself. Correspondingly, this method has disadvantages that the judgmentpolicy for the popularity of the file cannot be automatically adjustedto adapt to new businesses when the customers' businesses change.

Based on the above analysis, it may be found that it is time-consumingfor the decision-making center to collect the access data of the endcustomers in the content delivery system. Therefore, the storage of theobtained data is delayed. When determining the judgment policy for thepopularity of a file by the obtained data, it is necessary to ensure thereliability and timeliness of the center to issue the policy to theedge, which is relatively complicated. In contrast, the centralizedmanagement by the center is more convenient, and a protection policy maybe formulated. When an abnormality occurs in operation, the protectionpolicy may be triggered by the center.

If the judgment policy for the popularity of a file is determined by theedge node, since each node can determine a judgment policy for thepopularity of a file on the node, inconsistent judgment policies betweennodes may be caused. As a result, a same file may be judged as a popularfile or an unpopular file on different edge nodes. Consequently,disordered management is caused on the unpopular file management node.Correspondingly, the advantage of this method is that it can make fulluse of the computing power of the edge service, and the edge decisionbetter conforms to the access characteristics of the end customer at thecurrent node.

Combining the advantages and disadvantages of the two methods, apreliminary decision may be made regularly by the center, and on thebasis of the preliminary decision, the edge makes the final decisionaccording to the locally recorded popular and unpopular fileinformation. The following solutions are proposed.

Generation of a policy by the decision-making center: thedecision-making center regularly collects the access situation in theentire network for statistical analysis. The timing period may be set inhours. Since the probability of large changes in the business is low,high real-time performance is not required. According to the popularityof the business, the judgment policy for the popularity of a file ismade and issued to the edge node. The difference from the above methodis that no list of unpopular files/list of popular files is generated.The file accessed less than five times is determined as an unpopularfile and the number of times is synchronized to the edge.

Making the decision by the edge: the edge updates the policy and thedecision-making process is the same as the decision making by the edge.

By the cooperation of the decision-making center and the edge node, theimplementation of the decision-making center is relatively simple, andhigh real-time performance is not required. When the customers'businesses change greatly, the center can update the policy andsynchronize the policy to the edge.

The system in the exemplary embodiment of the present application use anunpopular file management node to centrally respond to requests forunpopular files, thereby reducing the bandwidth consumption whenresources are requested from the upstream node for unpopular files, andalso reducing the consumption of storage resources caused by cachingunpopular files in multiple edge nodes, and reducing the access pressureof the upstream node server. In addition, due to the popularity of theaccesses by the end customer, only a small part of requests needs to beredirected through the 302 technology. The hardware cost is low.

FIG. 1 is a flowchart of a method for processing an access request in acontent delivery system according to an exemplary embodiment. The methodshown in FIG. 1 comprises:

S101: A file access request is obtained.

In an exemplary embodiment, the file access request is a file accessrequest sent by an end customer, and the file access request comprisesidentification information of a desired file.

S102: It is judged, according to a preset unpopular file judgmentpolicy, whether a file corresponding to the file access request is anunpopular file, to obtain a judgment result.

In an exemplary embodiment, a corresponding file may be determinedaccording to the identification information of the desired file in thefile access request, and then according to the locally obtainedunpopular file judgment policy, it is determined whether the file is anunpopular file.

S103: It is judged, if the judgment result shows that the file is anunpopular file, and according to bandwidth usage state informationobtained in advance, whether the bandwidth usage state informationconforms to a preset judgment policy for the full use of the bandwidth,to obtain a judgment result.

In an exemplary embodiment, the bandwidth usage state information may bedetermined by the bandwidth occupancy state, or the proportion of thenumber of requests locally processed to all requests.

By judging whether the unpopular file management node is triggered torespond to the file access request for unpopular files, the forwardingof local file access requests to other nodes is effectively controlled,thereby controlling the number of forwarded requests. The fileprocessing efficiency is improved while ensuring the full utilization ofthe local resources.

S104: When the judgment result shows that the bandwidth usage stateinformation conforms to the judgment policy, an unpopular filemanagement node is triggered to respond to the file access request,wherein the unpopular file management node stores the file correspondingto the file access request.

In an exemplary embodiment, compared with the manner in which each edgenode handles unpopular file requests individually in the relatedtechnologies, the solution of the present application is to uniformlyhand over unpopular file requests received by the edge nodes to theunpopular file management node for processing. Therefore, the pressureof each edge node is reduced.

In the method embodiment of the present application, a file accessrequest is obtained; it is judged, according to a preset unpopular filejudgment policy, whether a file corresponding to the file access requestis an unpopular file, to obtain a judgment result; it is judged, if thejudgment result shows that the file is an unpopular file, and accordingto bandwidth usage state information obtained in advance, whether thebandwidth usage state information conforms to a preset judgment policyfor the full use of the bandwidth, to obtain a judgment result; and whenthe judgment result shows that the bandwidth usage state informationconforms to the judgment policy, an unpopular file management node istriggered to respond to the file access request. By judging whether anunpopular file management node is triggered to respond to a file accessrequest for an unpopular file, the forwarding of local file accessrequests to other nodes is effectively controlled, thereby controllingthe number of forwarded requests. The file processing efficiency isimproved while ensuring the full utilization of the local resources.

The method in the embodiment of the present application will bedescribed below.

In an exemplary embodiment, the judging, according to a preset unpopularfile judgment policy, whether a file corresponding to the file accessrequest is an unpopular file, to obtain a judgment result comprises:

searching, among locally stored files, a file corresponding to fileidentification information; and

determining, if the file is not found among the locally stored files,the state of the file according to a judgment policy for the popularityof the file obtained in advance.

In an exemplary embodiment, first, a determination is made as to whetherthe file is stored locally from the storage application of the edgenode, so as to use the locally stored file. Meanwhile, when the file isstored locally, the interaction with the upstream node and the unpopularfile management node is reduced to some extent, the use of networkbandwidth is reduced and the response speed to file access requests isimproved.

In an exemplary embodiment, the judgment policy for the popularity of afile is obtained in the following manner, comprising:

recording file access requests received accumulatively within a presetperiod of time; and

setting a the judgment policy for the popularity of a file according tothe recorded file access requests.

In this exemplary embodiment, the edge node may determine the number oftimes each file has been accessed according to the files requested bythe access requests recently, and obtain the number of times each filehas been accessed to set the judgment policy for the popularity of afile.

In an exemplary embodiment, the judging, according to bandwidth usagestate information obtained in advance, whether the bandwidth usage stateinformation conforms to a preset judgment policy for the full use of thebandwidth, to obtain a judgment result comprises:

obtaining a first number of file access requests to which the unpopularfile management node has been triggered to respond and a total number offile access requests obtained;

judging, according to the first number and the total number, whether theproportion information of the first number in the total number conformsto a preset judgment policy for the excessive proportion; and

determining, if the proportion information does not conform to thejudgment policy for the excessive proportion, that the bandwidth usagestate information conforms to the judgment policy for the full use ofthe bandwidth.

A determination is made as to whether the proportion of redirectedrequests in the total requests is greater than a set threshold. If so,the request will not be redirected. In this way, the proportion ofredirection operations is controlled:

Controlling the proportion of redirection operations avoids, if thecustomers' business is large in size or the node plan is changed, theredirection of a large number of requests intended to the node to othernodes to cause the node device and the node bandwidth to beunderutilized, so as to ensure that the node device and the nodebandwidth are fully utilized; in addition, controlling the number offile access requests responded by the unpopular file management nodeavoids the problem that the unpopular file management node receiving theredirection service cannot service normally due to request overload.

In addition, the threshold may be used to plan the size of the resourcepool of unpopular file nodes. The threshold is determined according tothe popularity of the business. Assuming that 10% of the files in thebusiness are relatively unpopular files, the threshold may be setslightly greater than 10%, for example 12%.

In an exemplary embodiment, the triggering an unpopular file managementnode to respond to the file access request comprises:

obtaining, when there are at least two unpopular file management nodes,region information and/or operator network information used to transmitinformation for each unpopular file management node;

selecting, according to the region information and/or operator networkinformation for each unpopular file management node, a target unpopularfile management node that conforms to the local region informationand/or operator network information; and

controlling the target unpopular file management node to respond to thefile access request.

The edge node considers the transmission performance between differentoperators or nodes in different regions. Therefore, for edge nodes indifferent operators or regions, it is necessary to consider usingunpopular file management nodes in the same operator and in the sameregion or nearby regions to respond, in order to improve thetransmission time of the request and improve the response efficiency.

In an exemplary embodiment, the selecting, according to the regioninformation and/or operator network information for each unpopular filemanagement node, a target unpopular file management node that conformsto the local region information and/or operator network informationcomprises:

obtaining domain name resolution information corresponding to the fileaccess request; and

determining, according to the domain name resolution information and theregion information and/or operator network information for eachunpopular file management node, an unpopular file management nodematching the domain name resolution information among the unpopular filemanagement nodes as the target unpopular file management node.

When the edge node obtains an unpopular file management node that may beused, it obtains the destination IP, to which the request can beredirected, through the agreed domain name resolved by the DNS, that is,the unpopular file management node that may be used in the region. Forexample, when an edge node in the Zhejiang Telecom needs to redirect arequest, first, it requests for resolution of an agreed domain name. Theunpopular node resolved by the domain name is the unpopular node that isconfigured for the operator Zhejiang Telecom and this region.

In an exemplary embodiment, the triggering an unpopular file managementnode to respond to the file access request comprises:

obtaining a server cluster in the unpopular file management node thatresponds to the file access request; and

routing the file access request to the server cluster.

In an exemplary embodiment, a server cluster may be selected as theresponse object of the file access request according to a hashing policyfor preset unpopular file cluster nodes. The method of triggering therequest may be to route a file forwarding request to the unpopular filemanagement node, so that the unpopular file management node knows therequest.

In an exemplary embodiment, the routing the file access request to theserver cluster comprises:

obtaining address information of the selected server cluster;

generating the file access request redirected to the selected servercluster according to the address information; and

sending the redirected file access request.

In an exemplary embodiment, by redirecting the request, the unpopularfile management node is triggered to respond, and also, the end customeris informed that the unpopular file management node will respond.

In an exemplary embodiment, the edge node may directly forward the fileaccess request to the unpopular file management node, and then send amessage to inform the end customer that the request is to be respondedby the unpopular file management node.

Comparing the above two methods, there are two messages in the lattermethod, and the interaction method does not comply with theclient-server message interaction method. Therefore, the former methodis preferred.

In the method embodiment of the present application, due to thepopularity of resource files accessed by the end customers, in the aidof the 302 technology, fewer edge node resources are used to serve theunpopular resource files. The bandwidth resource consumption and thestorage resource consumption can be reduced effectively.

FIG. 2 is a schematic view of a method for processing an access requestaccording to an exemplary embodiment. Combined with the system shown inFIG. 1 , the present application provides a method for processingaccesses by end customers, comprising the following processes and steps.

Process 1: The end customer initiates an access request to an edge nodecluster.

S1.1: The end customer initiates an access request to the serviceapplication of an edge node server.

S1.2: The service application requests the local storage application forresource files accessed by the end customer.

S1.3: The storage application processes the request from the serviceapplication. There are three branches as follows:

1) If the resource file may be found locally, the local storageapplication reads and responds to the resource file; and the processends.

2) If the resource file is not found locally and it is determined thatthis request is a popular resource request, the storage applicationrequests the upstream node for the resource, caches the resourcelocally, and responds the service application with the resource.

3) If the resource file is not found locally and it is determined thatthis request is an unpopular resource request, the storage applicationreturns information indicating that the resource is not found and thecurrent request is determined to be an unpopular resource request.

S1.4: The service application accepts and processes the contentresponded by the storage application. There are two branches as follows:

1) If the storage application responds with the resource file, theresource file is directly responded to the end customer; and

2) if the storage application responds with information indicating thatthe resource is not found and the current request is determined to be anunpopular resource request,

then, first, a server cluster in the edge node for the unpopularresource is selected by hashing; and

then, the current request is redirected to the target cluster throughthe 302 technology.

Process 2: The server in the edge node cluster responds the request tothe end customer. There are two branches as follows:

1) If the end customer receives a normal resource file, the currentrequest ends normally; and

2) If the end customer receives a 302 skip request, the end customercontinues using the URL redirected by the 302 technology.

Process 3: The end customer continues requesting the URL for the 302technology.

S3.1: The end customer initiates an access request to the serviceapplication of an edge node server for unpopular resources.

S3.2: The service application requests the local storage application forresource files accessed by the end customer.

S3.3: The storage application processes the request from the serviceapplication. There are two branches as follows:

1) If the resource file may be found locally, the local storageapplication reads and responds to the resource file; and

2) If the resource file is not found locally, then the storageapplication requests the upstream node for the resource, caches theresource locally, and responds the service application with theresource.

S3.4: The service application accepts and processes the contentresponded by the storage application.

Process 4: The server in the edge node cluster for unpopular resourcesresponds the end customer with the result.

FIG. 3 is a schematic comparison view of a method for processing anaccess request according to an exemplary embodiment. In the schematicdiagram shown in FIG. 3 , the method for processing random requests,from multiple end customers and to the server cluster in the edge node,for an unpopular file A comprises:

Without the optimized apparatus, each server cluster needs to requestthe upstream node for the unpopular resource file A for one time; andeach server cluster needs to cache the unpopular resource file A in thelocal cluster.

With the optimized apparatus, the request will be redirected to a fixedunpopular resource server cluster B, and only the unpopular resourceserver cluster B needs to request the upstream node for the unpopularresource file A for one time; and the unpopular resource file A needs tobe cached only in the unpopular resource server cluster B.

By comparison, it may be found that, by the method of the presentapplication, due to the popularity of resource files accessed by the endcustomers, in the aid of the 302 technology, fewer edge node resourcesare used to serve the unpopular resource files. The bandwidth resourceconsumption and the storage resource consumption can be reducedeffectively.

FIG. 4 is a schematic view of an apparatus for processing an accessrequest in a content delivery system according to an exemplaryembodiment. As shown in FIG. 4 , the apparatus comprises:

an obtaining module 401 configured to obtain a file access request;

a first judgment module 402 configured to judge, according to a presetunpopular file judgment policy, whether a file corresponding to the fileaccess request is an unpopular file, to obtain a judgment result;

a second judgment module 403 configured to judge, if the judgment resultshows that the file is an unpopular file, and according to bandwidthusage state information obtained in advance, whether the bandwidth usagestate information conforms to a preset judgment policy for the full useof the bandwidth, to obtain a judgment result; and

a processing module 404 configured to trigger, when the judgment resultshows that the bandwidth usage state information conforms to thejudgment policy, an unpopular file management node to respond to thefile access request, wherein the unpopular file management node storesthe file corresponding to the file access request.

In an exemplary embodiment, the first judgment module 402 comprises:

a searching unit configured to search, among locally stored files, afile corresponding to file identification information; and

a first obtaining unit configured to determine, if the file is not foundamong the locally stored files, the state of the file according to ajudgment policy for the popularity of the file obtained in advance.

In an exemplary embodiment, the second judgment module 403 comprises:

a second obtaining unit configured to obtain a first number of fileaccess requests to which the unpopular file management node has beentriggered to respond and a total number of file access requestsobtained;

a judgment unit configured to judge, according to the first number andthe total number, whether the proportion information of the first numberin the total number conforms to a preset judgment policy for theexcessive proportion; and

a determination unit configured to determine, if the proportioninformation does not conform to the judgment policy for the excessiveproportion, that the bandwidth usage state information conforms to thejudgment policy for the full use of the bandwidth.

In an exemplary embodiment, the processing module 404 comprises:

a third obtaining unit configured to obtain, when there are at least twounpopular file management nodes, region information and/or operatornetwork information used to transmit information for each unpopular filemanagement node;

a selection unit configured to select, according to the regioninformation and/or operator network information for each unpopular filemanagement node, a target unpopular file management node that conformsto the local region information and/or operator network information; and

a control unit configured to control the target unpopular filemanagement node to respond to the file access request.

In an exemplary embodiment, the selection unit comprises:

an obtaining sub-module configured to obtain domain name resolutioninformation corresponding to the file access request; and

a determination sub-module configured to determine, according to thedomain name resolution information and the region information and/oroperator network information for each unpopular file management node, anunpopular file management node matching the domain name resolutioninformation among the unpopular file management nodes as the targetunpopular file management node.

In the apparatus embodiment of the present application, a file accessrequest is obtained; it is judged, according to a preset unpopular filejudgment policy, whether a file corresponding to the file access requestis an unpopular file, to obtain a judgment result; it is judged, if thejudgment result shows that the file is an unpopular file, and accordingto bandwidth usage state information obtained in advance, whether thebandwidth usage state information conforms to a preset judgment policyfor the full use of the bandwidth, to obtain a judgment result; and whenthe judgment result shows that the bandwidth usage state informationconforms to the judgment policy, an unpopular file management node istriggered to respond to the file access request. By judging whether anunpopular file management node is triggered to respond to a file accessrequest for an unpopular file, the forwarding of local file accessrequests to other nodes is effectively controlled, thereby controllingthe number of forwarded requests. The file processing efficiency isimproved while ensuring the full utilization of the local resources.

An exemplary embodiment of the present application provides acomputer-readable storage medium having a computer program storedthereon that, when executed, implements the following steps of themethod, comprising:

obtaining a file access request;

judging, according to a preset unpopular file judgment policy, whether afile corresponding to the file access request is an unpopular file, toobtain a judgment result;

judging, if the judgment result shows that the file is an unpopularfile, and according to bandwidth usage state information obtained inadvance, whether the bandwidth usage state information conforms to apreset judgment policy for the full use of the bandwidth, to obtain ajudgment result; and

triggering, when the judgment result shows that the bandwidth usagestate information conforms to the judgment policy, an unpopular filemanagement node to respond to the file access request, wherein theunpopular file management node stores the file corresponding to the fileaccess request.

In an exemplary embodiment, the computer program implements, whenexecuted, the judging, according to a preset unpopular file judgmentpolicy, whether a file corresponding to the file access request is anunpopular file, to obtain a judgment result, comprising:

searching, among locally stored files, a file corresponding to fileidentification information; and

determining, if the file is not found among the locally stored files,the state of the file according to a judgment policy for the popularityof the file obtained in advance.

In an exemplary embodiment, the computer program implements, whenexecuted, the judging, according to bandwidth usage state informationobtained in advance, whether the bandwidth usage state informationconforms to a preset judgment policy for the full use of the bandwidth,to obtain a judgment result, comprising:

obtaining a first number of file access requests to which the unpopularfile management node has been triggered to respond and a total number offile access requests obtained;

judging, according to the first number and the total number, whether theproportion information of the first number in the total number conformsto a preset judgment policy for the excessive proportion; and

determining, if the proportion information does not conform to thejudgment policy for the excessive proportion, that the bandwidth usagestate information conforms to the judgment policy for the full use ofthe bandwidth.

In an exemplary embodiment, the computer program implements, whenexecuted, the triggering the unpopular file management node to respondto the file access request, comprising:

obtaining, when there are at least two unpopular file management nodes,region information and/or operator network information used to transmitinformation for each unpopular file management node;

selecting, according to the region information and/or operator networkinformation for each unpopular file management node, a target unpopularfile management node that conforms to the local region informationand/or operator network information; and

controlling the target unpopular file management node to respond to thefile access request.

In an exemplary embodiment, the computer program implements, whenexecuted, the selecting, according to the region information and/oroperator network information for each unpopular file management node, atarget unpopular file management node that conforms to the local regioninformation and/or operator network information comprises:

obtaining domain name resolution information corresponding to the fileaccess request; and

determining, according to the domain name resolution information and theregion information and/or operator network information for eachunpopular file management node, an unpopular file management nodematching the domain name resolution information among the unpopular filemanagement nodes as the target unpopular file management node.

The steps in the method according to the embodiment of the presentapplication may be adjusted in order, merged, and deleted according toactual needs.

The unit modules involved in the method for processing an access requestin the content delivery system according to the embodiment of thepresent application may be combined, divided, and deleted according toactual needs.

FIG. 5 is a block diagram of a computer device 500 according to anexemplary embodiment. For example, the computer device 500 may beprovided as a server. Referring to FIG. 4 , the computer device 500comprises a processor 501. One or more processors may be providedaccording to actual needs. The computer device 500 further comprises amemory 502 configured to store instructions executable by the processor501, for example application programs. One or more memories may beprovided according to actual needs. There may be one or more applicationprograms stored in the memory. The processor 501 is configured toexecute instructions to perform the method described above.

It may be understood by those skilled in the art that the embodiments ofthe present application may be provided as methods, apparatuses(devices), or computer program products. Therefore, the presentapplication may be in the form of an only hardware embodiment, an onlysoftware embodiment, or an embodiment combining software and hardware.Moreover, the present application may be in the form of a computerprogram product implemented on one or more computer-usable storage mediacontaining computer-usable program codes. The computer storage mediacomprise volatile and nonvolatile, removable and non-removable mediaimplemented in any method or technology for storing information (forexample computer-readable instructions, data structures, programmodules, or other data), including but not limited to RAMs, ROMs,EEPROMs, flash memories or other memories, CD-ROMs, digital versatiledisks (DVD) or other optical disk storages, magnetic cartridges,magnetic tapes, magnetic disk storages or other magnetic storagedevices, or any other media that may be used to store desiredinformation and may be accessed by a computer. In addition, as known toa person of ordinary skill in the art, the communication media usuallycontain computer-readable instructions, data structures, programmodules, or other data in modulated data signals such as carriers orother transmission mechanisms, and may include any information deliverymedia.

The present application has been described with reference to flowchartsand/or block diagrams of the methods, apparatuses (devices) and computerprogram products according to embodiments of the present application. Itshould be understood that each flow and/or block in the flowchart and/orblock diagram and the combination of flows and/or blocks in theflowchart and/or block diagram may be implemented by computer programinstructions. These computer program instructions may be provided to theprocessors of general-purpose computers, special-purpose computers,embedded processors, or other programmable data processing devices toproduce a machine, so that the instructions executed by the processorsof the computers or other programmable data processing devices producean apparatus that implements the functions specified in one or moreflows in the flowchart and/or one or more blocks in the block diagram.

These computer program instructions may be stored in computer-readablememories that can direct computers or other programmable data processingdevices to work in a specific manner, so that the instructions stored inthe computer-readable memories produce an article of manufactureincluding the instruction apparatus. The instruction apparatusimplements the functions specified in one or more flows in the flowchartand/or one or more blocks in the block diagram.

These computer program instructions may be loaded on computers or otherprogrammable data processing devices, so that a series of operatingsteps are executed on the computers or other programmable devices toproduce computer-implemented processing. Thus, the instructions executedon the computers or other programmable devices provide steps forimplementing the functions specified in one or more flows in theflowchart and/or one or more blocks in the block diagram.

Herein, terms “comprise,” “include” and variants thereof are intended tocover non-exclusive inclusion, so that an article or a device includinga series of elements not only includes these elements, but also includesother elements not explicitly listed, or further includes inherentelements of the article or the device. Without further limitation, anelement as defined by a statement “including a . . . ” is not exclusiveof additional identical elements in the article or the device of theelement.

Although the preferred embodiments of the present application have beendescribed, those skilled in the art can make additional changes andmodifications to these embodiments once they learn the basic creativeconcept. Therefore, the appended claims are intended to be interpretedas comprising the preferred embodiments and all changes andmodifications falling into the scope of the present application.

Apparently, those skilled in the art can make various modifications andvariations to the present application without departing from the spiritand scope of the present application. In this way, if thesemodifications and variations of the present application fall into thescope of the claims of the present application and their equivalents,the present application is intended to encompass these modifications andvariations.

INDUSTRIAL APPLICABILITY

In the present application, a file access request is obtained; it isjudged, according to a preset unpopular file judgment policy, whether afile corresponding to the file access request is an unpopular file, toobtain a judgment result; it is judged, if the judgment result showsthat the file is an unpopular file, and according to bandwidth usagestate information obtained in advance, whether the bandwidth usage stateinformation conforms to a preset judgment policy for the full use of thebandwidth, to obtain a judgment result; and when the judgment resultshows that the bandwidth usage state information conforms to thejudgment policy, an unpopular file management node is triggered torespond to the file access request. By judging whether an unpopular filemanagement node is triggered to respond to a file access request for anunpopular file, the forwarding of local file access requests to othernodes is effectively controlled, thereby controlling the number offorwarded requests. The file processing efficiency is improved whileensuring the full utilization of the local resources.

The invention claimed is:
 1. An access request processing method for acontent delivery system comprising: obtaining a file access request;judging, according to a preset unpopular file judgment policy, whether afile corresponding to the file access request is an unpopular file; inresponse to determining that the file is an unpopular file, judgingwhether bandwidth usage state information obtained in advance conformsto a preset judgment policy for full use of bandwidth; and triggering,in response to determining that the bandwidth usage state informationconforms to the judgment policy, an unpopular file management node torespond to the file access request, the unpopular file management nodestoring the file corresponding to the file access request; whereinjudging whether the file corresponding to the file access request is anunpopular file includes: searching locally stored files for a filecorresponding to file identification information; and determining, inresponse to the file corresponding to the file identificationinformation being not found among the locally stored files, a state ofthe file corresponding to the file identification information accordingto a judgment policy for file popularity obtained in advance.
 2. Themethod according to claim 1, wherein judging whether the bandwidth usagestate information obtained in advance conforms to the preset judgmentpolicy for full use of bandwidth includes: obtaining a first number offile access requests to which the unpopular file management node hasbeen triggered to respond and a total number of file access requestsalready obtained; judging, according to the first number and the totalnumber, whether proportion information indicating a ratio of the firstnumber to the total number conforms to a preset judgment policy forexcessive proportion; and determining, if the proportion informationdoes not conform to the judgment policy for excessive proportion, thatthe bandwidth usage state information conforms to the judgment policyfor full use of bandwidth.
 3. The method according to claim 1, whereintriggering the unpopular file management node to respond to the fileaccess request includes: obtaining region information and/or operatornetwork information used to transmit information for each of at leasttwo candidate unpopular file management nodes; selecting, according tothe region information and/or the operator network information for eachof the at least two unpopular file management nodes, a target unpopularfile management node from the at least two unpopular file managementnodes, the target unpopular file management node conforming to localregion information and/or operator network information; and controllingthe target unpopular file management node to respond to the file accessrequest.
 4. The method according to claim 3, wherein selecting thetarget unpopular file management node includes: obtaining domain nameresolution information corresponding to the file access request; anddetermining, according to the domain name resolution information and theregion information and/or the operator network information for each ofthe at least two unpopular file management nodes, an unpopular filemanagement node matching the domain name resolution information amongthe unpopular file management nodes as the target unpopular filemanagement node.
 5. A computer-readable storage medium storing acomputer program that, when executed by a processor, causes theprocessor to implement the method according to claim
 1. 6. A computerdevice comprising: a processor; and a memory storing a computer programthat, when executed by the processor, causes the processor to: obtain afile access request; judge, according to a preset unpopular filejudgment policy, whether a file corresponding to the file access requestis an unpopular file; in response to determining that the file is anunpopular file, judge whether bandwidth usage state information obtainedin advance conforms to a preset judgment policy for full use ofbandwidth; and trigger, in response to determining that the bandwidthusage state information conforms to the judgment policy, an unpopularfile management node to respond to the file access request, theunpopular file management node storing the file corresponding to thefile access request; wherein the computer program further causes theprocessor to: search locally stored files for a file corresponding tofile identification information; and determine, in response to the filecorresponding to the file identification information being not foundamong the locally stored files, a state of the file corresponding to thefile identification information according to a judgment policy for filepopularity obtained in advance.
 7. The device according to claim 6,wherein the computer program further causes the processor to: obtain afirst number of file access requests to which the unpopular filemanagement node has been triggered to respond and a total number of fileaccess requests already obtained; judge, according to the first numberand the total number, whether proportion information indicating a ratioof the first number to the total number conforms to a preset judgmentpolicy for excessive proportion; and determine, if the proportioninformation does not conform to the judgment policy for excessiveproportion, that the bandwidth usage state information conforms to thejudgment policy for full use of bandwidth.
 8. The device according toclaim 6, wherein the computer program further causes the processor to:obtain region information and/or operator network information used totransmit information for each of at least two candidate unpopular filemanagement nodes; select, according to the region information and/or theoperator network information for each of the at least two unpopular filemanagement nodes, a target unpopular file management node from the atleast two unpopular file management nodes, the target unpopular filemanagement node conforming to local region information and/or operatornetwork information; and control the target unpopular file managementnode to respond to the file access request.
 9. The device according toclaim 8, wherein the computer program further causes the processor to:obtain domain name resolution information corresponding to the fileaccess request; and determine, according to the domain name resolutioninformation and the region information and/or the operator networkinformation for each of the at least two unpopular file managementnodes, an unpopular file management node matching the domain nameresolution information among the unpopular file management nodes as thetarget unpopular file management node.
 10. A content delivery systemcomprising: an unpopular file management node; and a computer deviceincluding: a processor; and a memory storing a computer program that,when executed by the processor, causes the processor to: obtain a fileaccess request; judge, according to a preset unpopular file judgmentpolicy, whether a file corresponding to the file access request is anunpopular file; in response to determining that the file is an unpopularfile, judge whether bandwidth usage state information obtained inadvance conforms to a preset judgment policy for full use of bandwidth;and trigger, in response to determining that the bandwidth usage stateinformation conforms to the judgment policy, the unpopular filemanagement node to respond to the file access request, the unpopularfile management node storing the file corresponding to the file accessrequest; wherein the computer program further causes the processor to:search locally stored files for a file corresponding to fileidentification information; and determine, in response to the filecorresponding to the file identification information being not foundamong the locally stored files, a state of the file corresponding to thefile identification information according to a judgment policy for filepopularity obtained in advance.
 11. The system according to claim 10,further comprising: a decision-making center configured to: obtain fileaccess information in a file access request that occurs within a presetperiod of time and/or network bandwidth usage information correspondingto the file access request; according to the file access informationand/or the network bandwidth usage information, determine a judgmentpolicy for file popularity; and send the judgment policy for filepopularity to an edge node.
 12. The system according to claim 10,further comprising: an upstream node; wherein: the unpopular filemanagement node is configured to: in response to the file correspondingto the file access request being found locally, respond to the fileaccess request with the file corresponding to the file access request ina local storage space of the unpopular file management node; and inresponse to the file corresponding to the file access request being notfound locally, request the file corresponding to the file access requestfrom the upstream node; and the upstream node is configured to: obtainthe file corresponding to the file access request from a local storagespace of the upstream node upon receiving a file request from anunpopular file management node; and send the file corresponding to thefile access request to the unpopular file management node.
 13. Thesystem according to claim 10, wherein the unpopular file management nodeis configured to: obtain proportion information of file access requeststo which the unpopular file management node is triggered to respond bythe edge node in all file access requests obtained; and determine acapacity of a storage pool of the unpopular file management nodeaccording to the proportion information and a capacity of a storage poolof the edge node.